Skip to content

2.0 changelog #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
vLuckyyy wants to merge 8 commits into
base: master
Choose a base branch
from
Open

2.0 changelog #182

vLuckyyy wants to merge 8 commits into from
+138 −0

Conversation

@vLuckyyy
Copy link
Member

@vLuckyyy vLuckyyy commented Dec 1, 2025

No description provided.

@vercel
Copy link

vercel bot commented Dec 1, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
website Ready Ready Preview Comment Dec 5, 2025 7:54pm

@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Dec 1, 2025

Summary of Changes

Hello @vLuckyyy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the official changelog for EternalCore 2.0, a significant update focused on enhancing user experience, streamlining configuration, and boosting performance. It outlines numerous improvements, new features, and critical bug fixes, providing a clear and visual overview of the changes. The update also includes core system enhancements like Folia and PostgreSQL support, alongside a refactored internal database layer and improved documentation.

Highlights

  • New Changelog Document: A new documentation page, v2-changelog.mdx, has been added to detail all major changes introduced in EternalCore 2.0, providing a comprehensive overview of the update.
  • Documentation & General Improvements: The documentation has been redesigned for easier browsing, with dedicated pages for placeholders and permissions. All libraries have been updated, and full support for Minecraft 1.20.10 is confirmed.
  • Reworked Vanish System: The vanish system has been fully reworked, offering flexible toggles in config.yml for features like silent join, godmode, night vision, silent inventory access, and blocking various player actions.
  • New Commands & Features: New commands include /playtime to check total player time, and several 'fun' player-interaction commands like /elderguardian, /demoscreen, /lightning, /burn, /fireball, and /endscreen. AdminChat now supports a direct channel mode.
  • Core System Enhancements: The update introduces Folia support, full PostgreSQL support, a complete internal database layer refactor, and improved configuration structure with sections moved into separate classes. /heal now restores oxygen and supports custom health values, and /tprp can be limited by minY and maxY.
  • Bug Fixes: Several issues have been resolved, including missing permissions for gamemode shortcuts, a duplicate message in /enchant, /tprp no longer teleporting to the same player twice, and a fix for the GitHub API rate-limit warning in the update notifier.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Dec 1, 2025
View reviewed changes
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds the changelog for EternalCore 2.0. The changes are well-structured, including a new markdown file detailing the updates and a corresponding link in the documentation sidebar. My review focuses on the new changelog content, and I've provided a couple of suggestions to fix a broken image link and improve grammar for clarity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@vLuckyyy